@nedredmond are there any mouse events you didnt cover?
Asking because if this:

the other two are fixed by using pointer events to cover all interactions

@nedredmond are there any mouse events you didnt cover?
Asking because if this:

the other two are fixed by using pointer events to cover all interactions

I meant those two "other two" (touchstart and touchend) are handled by the consumer, and it works if they use pointer events instead, as in drawArea.pointerdown((e) => drawing.draw()) and drawArea.pointerup((e) => drawing.draw("stop")) (not sure I'm getting the syntax right, on my phone -- but you get it) which cover mouse, touch, and stylus events.

I think the user that reported the issue was seeing that the draw between touch start and touch end didn't work. With pointermove, it will.

Ah OK. I see. Thanks :)

@Fuzzyma, thanks for accepting my PR!

When might this be published? I'm using this for a bugfix at work (just migrated us from raphael) and I'd like to replace import to a git url to my own fork as soon as I can.

No rush for you of course, but would you let me know when the node package is published?

@nedredmond I merged from my phone so I couldnt publish right away :D. It should be available now.
Nice to hear that people still use this lib and even moving from something like raphael!

May I ask what you are building?

I refactored the drawing tools on Khan Academy exercises so that we can improve / extend them for accessibility. They let learners draw on the margins of their exercises while they work.

After the migration, it's broken for touch experiences. Whoops! Thanks for helping me get this fix in so quickly.

Uh interesting. Hope svg.js will serve you well :D